Comms Not Sent Workflow

A comm can have multiple delivery methods which may not be compatible with the target's delivery method. If a comms cannot be sent, CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. automatically raises a workflow - the Comms Not Sent workflow event. The reasons why delivery methods could not be implemented are written to a database table, CommsRequestNotSent. The status of the comm is changed to Not Sent. The reasons can be viewed via the Reasons Not Sent option in AgentView The graphical user interface of the CMP that is typically used by Customer Service Agents to access CMP customer and billing data. In versions prior to CMP 8.0, this was called the CMP GUI. in the Comms > Comms lower panel in the relevant Subscription A billing entity that incurs a charge. Examples include a network attached device whose usage you want to measure and charge for, or a monthly software subscription Summary screen or the Comms pane in the Event Summary screen Profile >Summary lower panel.

Comms Error Workflow

If a comm raises an error, the reasons for it are written to the database and the comms status is set to Error. The error can be viewed using the Error Details option in AgentView in the Comms > Comms lower panel in the relevant Subscription Summary screen or the Comms pane in the Event Summary screen Profile >Summary lower panel.